chore: uses system nim everywhere#19537
Conversation
Jenkins Builds
|
| scoop install --global ` | ||
| 7zip git dos2unix findutils ` | ||
| wget rcedit inno-setup ` | ||
| nim mingw-winlibs ` |
There was a problem hiding this comment.
added mingw-winlibs because
Running post_install script...done.
'nim' (2.2.6) was installed successfully!
'nim' suggests installing 'mingw-winlibs'.
There was a problem hiding this comment.
We should be pinning nim like Go above with @2.2.4 or similar and using hold:
admin@windows-01 MINGW64 ~
$ scoop hold --help
Usage: scoop hold <apps>
To hold a user-scoped app:
scoop hold <app>
To hold a global app:
scoop hold -g <app>
Options:
-g, --global Hold globally installed apps
|
for linux builds I need to update jenkins base docker image to contain |
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19537#2 🔹 ~13 min 🔹 fa38b65 🔹 📦 tests/ui package |
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19537#3 🔹 ~14 min 🔹 bb3dffc 🔹 📦 tests/ui package |
bb3dffc to
dc216e3
Compare
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19537#4 🔹 ~13 min 🔹 dc216e3 🔹 📦 tests/ui package |
dc216e3 to
0a5fb0d
Compare
✔️ status-desktop/prs/android/arm64/package/PR-19537#5 🔹 ~9 min 5 sec 🔹 0a5fb0d 🔹 📦 android/arm64 package |
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19537#5 🔹 ~14 min 🔹 0a5fb0d 🔹 📦 tests/ui package |
alexjba
left a comment
There was a problem hiding this comment.
Isn't it an option to preserve the single source of truth for the nim compiler version and use the one compiled by the deps-common make target? I think the USE_SYSTEM_NIM could probably be managed internally for status-go target whenever it's not provided by the user.
I was thinking this would be a good rule to have:
USE_SYSTEM_NIM provided by the user - use it everywhere
USE_SYSTEM_NIM not provided by the user - add the nimbus-build-system nim to PATH and enable USE_SYSTEM_NIM internally for all targets.
|
@alexjba : that is an option true, but since This PR merely brings in status-go version with that change : https://github.com/status-im/status-go/pull/7185/changes#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R220 and modifies system scripts to make sure |
|
also I would rather avoid |
What I meant is that we could probably avoid installing Nim on the host machines altogether (and ask developers to pin a specific local nim version). Instead, the main Makefile could configure the Nim path automatically by using the |
Not sure we can avoid it entirely..So unless the nim compilation part is producing these weird errors we're still stuck with these issues. |
✔️ status-desktop/prs/android/arm64/package/PR-19537#6 🔹 ~11 min 🔹 5ff23b4b 🔹 📦 android/arm64 package |
0a5fb0d to
26e1b96
Compare
✔️ status-app/prs/linux/x86_64/tests-nim/PR-19537#8 🔹 ~38 min 🔹 26e1b96 🔹 📦 tests/nim package |
✔️ status-app/prs/android/arm64/package/PR-19537#7 🔹 ~1 hr 9 min 🔹 26e1b96 🔹 📦 android/arm64 package |
✔️ status-app/prs/linux/x86_64/tests-ui/PR-19537#6 🔹 ~59 min 🔹 26e1b96 🔹 📦 tests/ui package |
ba3b2db to
8095b64
Compare
Jenkins BuildsClick to see older builds (87)
|
4963cfd to
652f6b9
Compare
f72b92f to
1004696
Compare
To fix windows build issues due to very long paths by nimbus-build-system - points status-go to bring in status-im/status-go#7185 - updates mac,windows host install scripts to include nim - updates linux dockerfile to install nim - updates linux docker image tag to use newer image
1004696 to
482c9b9
Compare
To fix windows build issues due to very long paths by nimbus-build-system